Session security for NTLM SSP-based clients must be configured to require NTLMv2 session security and 128-bit encryption.

Changes are coming to https://stigviewer.com. Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey

Session security for NTLM SSP-based clients must be configured to require NTLMv2 session security and 128-bit encryption.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-225056	WN16-SO-000400	SV-225056r569186_rule		Medium

Description
Microsoft has implemented a variety of security support providers for use with Remote Procedure Call (RPC) sessions. All of the options must be enabled to ensure the maximum security level.

STIG	Date
Microsoft Windows Server 2016 Security Technical Implementation Guide	2023-03-02

Details

Check Text ( C-26747r466070_chk )
If the following registry value does not exist or is not configured as specified, this is a finding. Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\ Value Name: NTLMMinClientSec Value Type: REG_DWORD Value: 0x20080000 (537395200)

Fix Text (F-26735r466071_fix)
Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Network security: Minimum session security for NTLM SSP based (including secure RPC) clients" to "Require NTLMv2 session security" and "Require 128-bit encryption" (all options selected).